-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare ParselyTracker
for Kotlin migration
#98
Prepare ParselyTracker
for Kotlin migration
#98
Conversation
Reasons: to reduce responsibilities of `ParselyTracker` and introduce unit tests coverage for "no internet connection" case
Instead of returning `-1` in case of missing interval
BREAKING CHANGE: this method was part of the public contract but I can't find a justified value of it
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #98 +/- ##
==========================================
+ Coverage 68.24% 69.25% +1.00%
==========================================
Files 16 18 +2
Lines 359 361 +2
Branches 52 52
==========================================
+ Hits 245 250 +5
+ Misses 97 95 -2
+ Partials 17 16 -1 ☔ View full report in Codecov by Sentry. |
|
||
import java.util.Formatter | ||
|
||
object Logging { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At this moment I can't make this object internal
because it won't be visible for Java classes. When the migration from Java to Kotlin is completed, I'll make sure to make it internal
.
In case of an empty `url` parameter, the SDK should not crash the application. The logging SDK is likely not as critical to the consumer business flow to the degree, that providing an incorrect argument would kill the whole process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
Description
This PR is a set of changes that aim to reduce the size of
ParselyTracker
to reduce the responsibilities of this class and make the transition from Java to Kotlin more readable and easier to review.Testing
I see no need for manual tests of this PR. Unit and functional tests suite should be just fine.